##[group]The deploy tool's tests
npm run test:deploy
##[endgroup]
shell: bash -e /home/runner/_temp/18dfa795b5ff2e5b.sh

> test:deploy
> node --test "scripts/deploy/*.test.mjs"

error: no matching package named `base64` found
location searched: crates.io index
required by package `g1t-api v0.1.0 (/home/runner/work/repo/apps/api)`
note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
help: if this error is too confusing you may wish to retry without `--offline`
✔ the manifest matches every wrangler config in the repository (78.970817ms)
✔ every wrangler.jsonc is found, and only checked-in ones (16.864194ms)
✔ problems are found: an unlisted config, a later-stage binding, a wrong database, an unnamed KV (20.573098ms)
✔ stages follow bindings: nothing binds to a unit that ships after it (0.54916ms)
✔ Rust workers build with the shared script and the same wasm-opt level (0.70886ms)
✔ shared crates and packages are read from workspace metadata (51.978744ms)
✔ the runner's image is built from the runner crate and what it uses, on the base its lock names (0.4473ms)
✔ services/runner/base.json records the base its folder builds (8.801157ms)
✔ an image's hash ignores line endings, and its tags say what they are (124.192246ms)
✔ only the lockfile entries the runner is built from name its image (0.787601ms)
✔ the runner's deploy config names its image by reference, beside its wrangler.jsonc (64.757055ms)
✔ the registry is asked for an image's manifest, without Docker (1.724271ms)
✔ a push counts only when it ends with a digest, and is tried again (1.045161ms)
✔ a static Linux binary is told from a dynamic one (1.027021ms)
﹣ path dependencies agree with Cargo's own resolved graph (2018.0963ms) # cargo metadata could not resolve offline
✔ every import that leaves a unit's folder is covered by its dependencies or inputs (101.300687ms)
✔ a shared crate's change reaches every unit built from it, and no other (0.770311ms)
✔ a shared package's change reaches what imports it (0.246881ms)
✔ own folders, declared inputs and root files (0.51127ms)
✔ a Cargo.lock change reaches only crates that use what changed (0.451931ms)
✔ a package-lock change reaches through workspace links (0.63268ms)
✔ decide: changed units deploy, others wait, unknown ones deploy (0.542921ms)
✔ decide: --force deploys unchanged units; a commit missing from history deploys (0.15026ms)
✔ decide: Cargo.lock counts only where it reaches (0.38869ms)
✔ decide: the runner's image rebuilds only when what it is built from changed (0.152241ms)
✔ the plan as data: migrations, and each stage's units in jobs that share a build (0.86745ms)
✔ units are picked by short name, folder or Worker name (0.423521ms)
✔ a CI job installs only what its units need (0.7175ms)
✔ a deploy is annotated with its commit, and read back (0.266ms)
✔ the live commit: the live version's, looking through secret changes (0.40421ms)
✔ Wrangler's output: pending migrations and the version a deploy made (0.3742ms)
✔ the pool runs everything, no more than its limit at once (87.178405ms)
✔ self-hosting builds every Rust service the manifest says it runs (0.820611ms)
✔ docs/SELF_HOSTING.md's table names every unit (0.37452ms)
✔ resolveStack works on a manifest with no workspace crates or packages (6.170446ms)
✔ decide: a commit older than what runs is never deployed by accident, even forced; --rollback means it (0.19973ms)
✔ a deploy by hand reports to the repository on g1t, and a workflow's does not (1.376751ms)
scheduler: g1t-webhooks (* * * * *) is still running from the last time; skipped
scheduler: g1t-webhooks (* * * * *): 200 {"outcome":"exception"}
✔ fields read numbers, ranges, lists and steps (2.116712ms)
✔ the services' crons match when hosted g1t's would fire (1.990992ms)
✔ what is due is each matching cron of each service (0.5115ms)
✔ a run asks Wrangler for the handler, and a slow one is not doubled (99.678525ms)
ℹ tests 41
ℹ suites 0
ℹ pass 40
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 3100.198233
